feat: add TracePlugin for structured resolution tracing#627
Open
hey-amanthakur wants to merge 1 commit into
Open
feat: add TracePlugin for structured resolution tracing#627hey-amanthakur wants to merge 1 commit into
hey-amanthakur wants to merge 1 commit into
Conversation
Add a TracePlugin that hooks into the resolver lifecycle to record structured trace entries for every resolution step. Each entry captures the hook name, request details, result, and timestamp as a machine-readable object instead of plain text strings. This allows developers to filter, search, and programmatically analyze resolution traces, complementing the existing resolveContext.log which outputs unstructured text.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a TracePlugin that hooks into the resolver lifecycle to record structured trace entries for every resolution step. Each entry captures the hook name, request details, result, and timestamp as a machine-readable object instead of plain text strings.
This allows developers to filter, search, and programmatically analyze resolution traces, complementing the existing resolveContext.log which outputs unstructured text.